[00:00] In the previous topic, we familiarized ourselves with Docker containers and volumes and created a multi-container application with Docker Compose. In this topic, we'll use those skills to build out a testing environment meant to mirror what we could be running in a production environment. Creating a cloned testing environment would allow us to test out Ignition upgrades and test configuration changes to a similar environment without causing any disruptions to production. Our production environment consists of two Ignition gateways one being for the front end and one for the back end. These two gateways communicate with each other via a Gateway Network Connection. There's also a database server running MariaDB. And then an SMTP server that's used for email notifications. These two servers communicate with our backend server. Let's look at what this architecture will look like for us in our Docker Compose application we'll be building out. The blue boxes in the center represent our containers or services within our application.

[01:03] We have two that are running our frontend and backend Ignition gateways. Then one will contain our database software. And the last one will contain our SMTP server. the arrows represent the different connections we'll need we need to be able to access our frontend and backend Gateway web pages as well as our SMTP server's web interface. Our two gateways must be able to communicate with each other via the Gateway Network. Finally our backend Gateway will house connections to the database and SMTP containers. In the next few lessons, we'll walk through the process of setting up these containers and their connections within our application and we'll develop some hands-on experience using Ignition with Docker.